Network-enabled, extensible metering system

ABSTRACT

To allow meter data users to have access to needed information and at the same time address the rapidly shifting requirements of the deregulated marketplace, a new business model employs a common metering device that measures raw data and a system composed of independent services or applications that collect and process raw metered data and then make that data available to interested parties. This new model removes the dependence upon an automatic meter reading (AMR) system provider, as the sole provider, by creating a system to enable a competitive environment where services (applications, information, networking, etc.) rather than systems are selected and paid for on a leased or pay-per-use basis.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 09/798,084,filed Mar. 2, 2001, titled “Network-Enabled, Extensible MeteringSystem,” now U.S. Pat. No. 7,046,682, which is hereby incorporated byreference, and which is a continuation-in-part of application Ser. No.09/022,718, now U.S. Pat. No. 6,396,839, filed Feb. 12, 1998, titled“Remote Access to Electronic Meters Using a TCP/IP Protocol Suite,”which is hereby incorporated by reference and which claims priority toProvisional Patent Application Serial No. 60/039,716, filed Feb. 12,1997.

FIELD OF THE INVENTION

The present invention relates generally to the field of utility metering(including gas, electric, water and energy metering). More particularly,the present invention relates to the integration of network systems andutility meters.

BACKGROUND OF THE INVENTION

The above-cited U.S. patent application Ser. No. 09/022,718 discloses asystem generally involving electronic meters and automatic meterreading, and more particularly TCP/IP-enabled electronic utility metersfor remote two-way access over local and wide area networks. The presentinvention is related in that it involves the use of TCP/IP-enabled,extensible utility meters in a new business model and system. Furtherbackground information about the business model aspect of the presentinvention is provided below.

Business Models

Currently, meter manufacturers sell meters to make money. Some revenueis generated from metering system sales, but these systems are generallyviewed as just another mechanism for selling additional meters. Metermanufacturers compete by providing better metering capabilities andfunctionality at a lower price.

Any given type of meter, whether it is water, electric, energy, or gas,measures a bounded set of quantities. These quantities represent the rawdata collected by the device. Meter manufacturers cannot use this rawmetered data as a way to differentiate themselves from theircompetitors. Therefore, at the factory, they load their meter's firmwarewith embedded capabilities, improved accuracy, or other applications(e.g., time of use (TOU), power quality (PQ) and/or alarm monitoring).These firmware applications use the meter's core set of data to computethe information that their meter data users (MDUs) need. To hedgeagainst the uncertainty of deregulation, meter data users (such asutility distribution companies (UDC), energy service providers (ESP), ormeter data management agencies (MDMA), etc.) often purchase, at a lowprice, fully capable meters with all or some of their capabilitiesdisabled (i.e., “turned off”). When additional functionality is needed,the MDU must purchase a license (or “key”) that gives it the ability toenable (“turn on”) the desired function in a meter. This method ofselectively turning on meter functions allows the meter manufacturer tocreate new license-based pricing models to make its product more costcompetitive. Thus, in reality, the meter must still be manufactured withall of the necessary hardware and applications in order to support thefullest possible range of functionality in an effort to more efficientlyaddress possible future metering needs.

This business model has several drawbacks:

-   -   1) increased functionality in the meter requires an increase in        processing power (e.g., ROM, RAM, EEPROM, etc.) and a        commensurate increase in cost;    -   2) the memory available “under the glass” in a meter is finite        (i.e., in order to add an option you must remove another option        or increase the memory);

3) to upgrade or re-program a meter requires that a meter techniciandrive to the location, physically remove the meter (or switch it outwith a replacement meter) and then return it to the “meter shop” wherethe upgrade can occur; after the upgrade is complete, the meter must bereturned and re-installed;

-   -   4) different meters require different interfaces and different        communications protocols for retrieving data;    -   5) increased application complexity in the firmware of the meter        leads to a higher probability of errors that may require        upgrades;    -   6) increased application functionality housed in the firmware of        the meter typically requires complex configuration or        programming of the end-device, which greatly increases the        system management, coordination, and synchronization; and    -   7) meter inventory must be increased in order to accommodate        different configurations, functionalities, and versions of        metering devices.

With the advent of improved communication technology, manufacturers arenow able to add modem, network, and radio-frequency (RF) connectivity totheir meters, thus permitting remote communications between meters andvarious meter data retrieval systems (e.g., automated meter reading(AMR) systems). However, there are limitations associated with thesemethods of remote communications:

-   -   1) wireless communication with the meter is often limited to off        peak hours determined by the various network providers;    -   2) satellite-based communications are limited to line of sight        communication between the meter and the satellite, thus limiting        the times when the meter may be contacted;    -   3) wireless and orbital satellite networks are costly, often        billing per byte of data transmitted, thus limiting the amount        of data which can effectively be transmitted.

Existing AMR systems are also limited in that they require severallayers of applications and interfaces in order to communicate withconnected meters. These layers implement the various communicationsprotocols used by the numerous meter manufacturers and the variouscommunications technologies that can be used to communicate with a meter(e.g., RF communication, satellite-based communication, etc.). As thesemeters are constantly revised, so are their communications protocols,requiring similar modifications to the AMR system. Industry standardsintended to unify the communication and device protocols typically fallshort by setting minimum requirements for compliance and/or providingmanufacturer-specific mechanisms to allow variability andcustomizations. Therefore, AMR systems still often requiremeter-specific knowledge (e.g., communications and device protocols) toread the required data from meters offered by different manufacturers.Even with the current metering standards, the addition of a new ordifferent meter would typically require additions and/or modificationsto an AMR system. The increasing variety of meters presents an almostinsurmountable challenge to the automated meter reading industry.

Deregulation of the electricity metering industry has created even morechallenges. Prior to deregulation, a utility was responsible forgenerating, distributing, and transmitting electricity as well aspurchasing, storing and installing metering devices, collecting metereddata and processing customer billing. Now, with deregulation slowlybeing implemented throughout the United States, those duties andresponsibilities that were the exclusive responsibility of the utilitycan now be divided among several service companies and providers who allneed access to the meter and the meter data. All of these companiesrequire access to either the data collected from the metering devices(e.g., power quality, outage, etc.) or to the calculated/processed data(e.g., quadrant data; validated, estimated, and edited (VEE) data, etc.)for their internal use (load management and monitoring, forecasting,etc.).

Today there are two prevailing AMR System business models. We refer tothese as: 1) the exclusive ownership model (depicted in FIG. 1), and 2)the service bureau model (depicted in FIG. 2). Certain AMR Systemdeployments utilize a mixture of these two models in order to establisha workable business case, but we will discuss these models individually.FIG. 1 depicts the exclusive ownership business model and shows twoscenarios for AMR Systems that utilize public communication networks andprivate communication networks, or so-called fixed networks. FIG. 2depicts the service bureau business model and shows two scenarios forAMR Systems that utilize public communication networks and privatecommunication networks. A key difference between the public and privatetype communication networks is that the private network requiresadditional up-front cost to deploy the infrastructure of the fixednetwork to blanket one or more service areas. Although FIGS. 1 and 2separate the public and private communications, AMR Systems exist thatcan utilize a combination or mix between public communication networksand private communication networks.

In the exclusive owner business model (FIG. 1), the meter data users(MDUs) (i.e., ESPs, UDCs, MDMAs, etc.) purchase an AMR system with asignificant up-front cost. In this business model, a particular MDU thatis purchasing an AMR System is typically only interested in how thepurchased AMR System will address its specific needs as identified inits business case. The MDU typically develops a business case thatjustifies the initial AMR System cost based on both measurable andnon-measurable benefits. Some of the measurable benefits include:

-   -   1) meter reading staff and infrastructure reductions,    -   2) cost reductions for hard-to-access meter reading,    -   3) connect/disconnect staff reductions,    -   4) accurate and timely outage restoration,    -   5) reduction in theft or tampering.

Some of the non-measurable benefits include:

-   -   1) faster and more frequent meter readings, thus yielding a        higher level of customer service/retention,    -   2) better positioned for competition in a deregulated energy        market,    -   3) ability to provide other types of services (i.e., new rates,        flexible billing, etc.),    -   4) other future uses for the metered information.

Taken alone, the measurable benefits listed above typically do notjustify the expense incurred by purchasing an AMR system. Consequently,the number of large AMR System deployments has not reached expectations.

In the service bureau business model (FIG. 2), a service bureau (e.g.,MDMA) purchases an AMR system with a significant up-front cost, and thenprovides access to the collected meter data to subscriber MDUs. Thisbusiness case is built on the value of the metered information. Itassumes the service bureau will recoup the cost of the AMR system byselling meter reads or metered information to multiple MDUs (ESPs, UDCs,etc.). From the perspective of the MDU, many of the quantifiable andnon-quantifiable benefits discussed above can be met using this model,with timely access to the correct set of metered information. In thismodel, the MDUs do not own and operate the AMR System, which is theresponsibility of the service bureau operator. In this model, the MDUsmust pay for the information they require. This reduces the up-frontcosts for the MDUs over purchasing their own AMR System and providesthem with a pay-per-use model. The service bureau model could createsome conflicts, or perceived conflicts, when competing MDUs utilize thesame service bureau for metered information. E.g., how can “MDU 1”differentiate its end-user offerings and services from a competitor,“MDU 2,” that utilizes the same service bureau and consequently hasaccess to the same type of metered information? In the service bureaumodel, the MDUs need to be able to add value by developing or buyingapplications that allow them to differentiate themselves from theircompetitors.

In both business models, the AMR supplier's business case is to developand sell AMR Systems and maintenance agreements. This business caseassumes that the development investment for an AMR System can berecouped through many AMR System sells. In the exclusive owner businessmodel, the AMR System supplier is typically confronted with a customerwho wants an AMR System customized to handle his/her specific businessprocesses. These types of AMR System sales usually require the AMRsupplier to perform customer specific development. AMR System sells ofthis type, made by an AMR supplier, increase the AMR supplier's overalldevelopment costs, deployment costs, long-term maintenance costs, andupgrade costs. In the service bureau business model, the AMR supplier isconfronted with a customer who requires an AMR System that has adifferent set of requirements from the AMR System of the exclusiveownership model. The AMR System sold to operate as a service bureau mustaccommodate many different MDUs and their business processes, and mustalso control access to the metered data. E.g., “ESP A” cannot read themetered information for a customer of “ESP B.” The service bureau AMRSystem is more complex because this system must accommodate all of theMDU's needs while controlling or limiting access in a secure manner. TheAMR System suppliers have a problem in creating a workable business casebecause they make a significant development investment and cannot affordfinancially or from a risk management point of view to limit theirsystems to one business model or the other. In today's uncertainenvironment, it is not clear if both business models will survive thederegulation evolution. The AMR System suppliers, therefore, mustidentify a way to develop a system that covers all requirements for bothbusiness models, is customizable, flexible, easily adaptable, etc.

In either of the above business models, the MDUs and the service bureauoperators are dependent upon the sole AMR System supplier to reactquickly to solve system problems, and address new requirements that mayevolve from the evolving deregulation process. Since the AMR Systemsdeveloped today are proprietary and closed, this dependency upon a soleprovider is a weak link in terms of risk management for the MDUs andservice bureau operators. Competition within the volatile deregulatedenvironment hinges upon AMR System providers' ability to respond rapidlyto customer needs.

SUMMARY OF THE INVENTION

To allow meter data users to have access to needed information and atthe same time address the rapidly shifting requirements of thederegulated marketplace, there is a need for a new business model, and anew apparatus and system for implementing such a business model. Thepresent invention meets this need by providing a common metering devicethat measures raw data and a system composed of independent services orapplications that can collect and process raw metered data and then makethat data available to interested parties. This new model is intended toremove the dependence upon an AMR System provider, as the sole provider,by creating a system concept to enable a competitive environment whereservices (applications, information, networking, etc.) rather thansystems are selected and paid for on a leased or pay-per-use basis.

A networked-based, extensible metering system in accordance with thepresent invention comprises a network server, a wide area networkcoupled to the network server, and a plurality of network-enabled meterscoupled to the network. The meters collect data and the network serverprovides at least one metering application to the meters. In addition,the meters may be programmed to communicate via a predefined protocoland to deliver a protocol interface to a storage medium on the network,which enables the network to provide the protocol interface to users orapplications requiring information from the meters and theusers/applications to communicate with the meters to access the requiredinformation.

Other aspects of the present invention are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically depicts two business scenarios that reflect currentbusiness models for exclusively-owned AMR systems.

FIG. 2 schematically depicts two business scenarios that reflect currentbusiness models for service bureau AMR systems.

FIG. 3 illustrates a business model provided by the present invention.

FIG. 4 illustrates revenue flow as a result of the sale/lease ofmetering services developed to work in a business model provided by thepresent invention.

FIG. 5 illustrates an exemplary embodiment of a Network-enabled,Extensible Metering System in accordance with the present invention.

FIG. 6 is a data flow diagram that illustrates the data flow in theNetwork-enabled, Extensible Metering System.

FIG. 7 illustrates the components of an embedded, network-enabledmetering device and communications adapters used to connect the deviceto a network.

FIG. 8 schematically depicts various methods for connecting legacymetering devices to the Network-enabled, Extensible Metering System.

FIG. 9 depicts an end-user (“outside the fence”) to Network-enabled,Extensible Metering System (“inside the fence”) scenario.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention introduces a new method for generating meteringrevenue using new, faster and improved communication and devicetechnologies. In this system and business model, a new meter apparatusfor collecting and storing metered data and information is part of avirtual machine as is the network application system of which it is apart. By residing on the network, the meter information becomes readilyaccessible to other devices, applications, and users on the network.Using new object-oriented, embedded networking technologies (e.g., SunMicrosystems' Java®/Jini®, Microsoft's Universal Plug and Play®, etc.),service discovery protocols, and security mechanisms, devices (i.e.,meters) and services (i.e., data collection, storage, validation, TOU,etc.) are accessible to MDUs (such as, ESP, UDC, and MDMA) that needaccess to raw or metered information.

An exemplary embodiment of the present invention will now be describedfrom the perspectives of the business model and the system.

Business Model

FIGS. 3 and 4 illustrate how application services may be purchased (at aone-time cost), leased (on a time-of-use or pay-per-use basis), ordeveloped in-house for processing raw and/or real-time meter data. Inthe system shown in FIG. 3, MDUs use metering service applications toprocess raw data collected from networked meters. The MDUs are denotedas follows in the various scenarios depicted in FIG. 3: “ESP1,” “UDC,”“ESP2” in the Service Bureau model; “MDMA” in the Purchased Servicesmodel; and “UDC” in the Leased Services model. Also, in FIG. 3, thesuite of services applications are:

-   -   1) CS—Collection Services    -   2) TOU—Time of Use Services    -   3) DF—Data Formatting Services    -   4) DR—Data Repository Services    -   5) VEE—Validated, Estimated and Edited Data Services    -   6) BS—Billing Services    -   7) MS—Monitoring Services    -   8) PQ—Power Quality Analysis Services    -   9) FC—Forecasting Services.

FIG. 4 shows the revenue flow as services that process meter data areleased or purchased. This business model allows MDUs to have secureaccess, via application programming interfaces (APIs), to data collectedby networked meters. With the deregulation of the electricity meteringindustry, metering data processing protocols are becoming standardized.This invention provides an open, standardized system that permits thehigh degree of customization and flexibility demanded by a deregulatedmetering environment. This enables vendors and meter data users todevelop standardized data processing applications and value-addedapplications for sale, lease or in-house usage. FIGS. 3 and 4 show asample of the type of services that benefit from defined/standardizedAPIs to address AMR operations. As shown in FIG. 4, some of theapplications are developed in-house by the respective MDUs whereasothers are leased or purchased for a fee (as indicated by the “$” signsand arrows).

Thus, the present invention may be implemented in a system thatcomprises network-based applications and network-enabled meters(electrical, gas, energy and water) that can provide full or part-time,secure connectivity between the meters and layered business applicationsusing the Internet. Moreover, by employing object-orientedinter-networking technologies for embedded devices technology, thissystem provides a suite of products including meters, core services andnetworked applications that make meter information available tointerested parties. The inter-network services are expected to providecommon communications protocols, discovery protocols, namespacemanagement (i.e., Directory or Lookup Service), leasing/pay-per-useservices, and security (especially secure access to network-enabledmeters).

System and Apparatus

FIG. 5 schematically depicts an exemplary embodiment of aNetwork-enabled, Extensible Metering System in accordance with thepresent invention. As shown, metering devices 1 collect data on ametered service 2 and communicate the collected data via variouscommunications devices 3 and 4 (antenna and modem, respectively) to aTCP/IP network 5. Also on the network 5 are various network devices forstoring and processing the meter data; network servers 6; a directoryserver 7 for device location and interface location; and a databaseserver 8 for storing raw and processed meter data and the meters'communication interfaces. This system allows the metering devices toupload raw metered data (e.g., kVARh, kWh, load profile, etc.) to thenetwork 5 for processing and storage in the database 8 and the networkservers to download real-time applications (e.g., power qualitymonitoring, alarm management, etc.) directly to a meter'sleased/reserved memory and, based upon meter memory constraints, on aper-lease or on an as-needed basis.

FIG. 6 depicts data flow in the system. Instead of the system havingembedded knowledge of meter protocols and specific communications accessmethods, the meter device itself delivers its protocol interface to thenetwork-side Directory Service. As shown, in this system, a meter datauser, or MDU, installs a meter (with an embedded networking device) at acustomer's location. When the meter is connected to the network, itnotifies the network's Directory Service that it is connected and readyto communicate (step S1). At the same time, the meter uploads itscommunications interface to the network database (step S2). A user or anapplication (e.g., a data retrieval system) requiring information fromthe meter asks for the meter's location from the Directory Service (stepS3) and downloads the meter's communications interface (step S4). Nowable to communicate directly with the meter without having priormeter-specific protocol knowledge, the user or application communicatesdirectly with the meter and accesses the needed information (step S5).Access to the applications necessary to process the meter's informationmay be made available to the MDU on a pay-per-use and/or pay-by-timelease basis. This process allows meter data users to purchase a simplemeter (with embedded networking technology) with little to no embeddedapplications. Applications needed to extend the functionality of a metercan then be developed, leased or purchased on an as-needed basis andexecuted at the network level. This system could also push neededapplications out to the meter for execution at the meter level (e.g.,real-time functions such as power quality monitoring, alarm monitoring,etc). Since the traditional in-meter applications are removed from themeter and placed at the network level, new applications can be easilydeveloped and quickly implemented via the network to support futurefunctionality and features that are not yet needed in today'sderegulated environment. These applications may be purchased or leasedfrom a third party vendor or developed by the meter data user.Applications developed by the meter data user could be sold or leased toother meter data users to generate additional revenue. This changes thebusiness model for metering from a model where money is made on themeter device itself to a service-based model where the information ispaid for each time it is accessed or used. In this model, the meteredinformation becomes the revenue generator.

FIG. 7 depicts the components of an embedded, network-enabled meteringdevice and the possible communications adapters used to connect thedevice to a network (LAN or WAN). As shown, such a metering device couldinclude a measuring device, an accumulator for collecting the metereddata, memory for storage, and some type of connector or port forconnecting to a communications adapter. The various communicationsadapters would accommodate telephony, WAN CDPD, wireless Ethernet, andLAN Ethernet. Such a system would be easily expanded as communicationstechnologies improve and are expanded. The network-enabled meter becomesa simple metering device that collects and stores raw (unprocessed)meter data (i.e., the quantities that can be measured are finite). Thevariety of communications adapters provide the meter with the means tocommunicate with the users and applications on the network system.

FIG. 8 illustrates various methods for connecting legacy meteringdevices (e.g., electromechanical or electronic meters that are notnetwork-enabled) to the system. One manner of enabling a meter tointerface with a network would be composed of either an internal orexternal hardware adapter that would provide the embedded networkconnectivity. Another way involves an interface application located onthe system's network end. The adapters and system application wouldcontain the necessary communications and device interface informationthat would enable any user or device connected to the network tocommunicate with the legacy metering device.

FIG. 9 illustrates an end-user to Network-enabled, Extensible MeteringSystem scenario. In this scenario, network-enabled applications residingon a meter data user's (such as an energy service provider) networkwould have direct access (via radio-frequency, Internet, etc.) to themetered data of an end-user (e.g., a residential or acommercial/industrial customer). The meter data user side of the systemwould store the metered data in either independent or cumulative datarepositories. Additionally, the meter data user side may is able todownload or push real-time meter applications out to the metering deviceas needed. On the end-user side of the system (furnished with variousnetwork-enabled devices: a display, a meter, home automation devices,etc.), the user may lease or purchase a service package of applicationsfrom the meter data user that enables the user to perform a variety offunctions, e.g., TOU analysis, load shedding, power quality monitoring,etc.

In the inventive system, the network-enabled meter ceases to be the solerevenue-generating commodity for manufacturers. Instead, the meter andthe software systems that access and process its data become acontinuous source of revenue. The meter becomes a simple device thatrequires no programming and fewer upgrades. The meter's functionality isno longer limited by the volume “under the glass” but becomes virtuallyunlimited by having the functionality residing on the network andaccessed on an as-needed basis by the networked applications. Networkedapplications use the same service infrastructure as the networked meter.E.g., the networked applications use the network discovery, join andlookup services to find other application services just as applicationsuse network infrastructure to find meter services. Networkedapplications register the services they offer with the Lookup services,just as the meter does. This allows both networked meters and networkedapplications to work in a transparent federation of services. In orderfor applications and meters to cooperate in a federation of services,the service interfaces must be predefined into a set of Open APIs. Theseapplications can include storage of metered information, load profiling,data aggregation, power quality monitoring, tariff calculations, outagenotifications, etc. Meter data users may decide which applications theyneed and either choose the application provider or develop the neededapplication in-house. If an application provider were selected, then theapplication would be paid for on either a per-use basis or leased for aset period of time. New or expanded functions and features could beeasily added to the system and just as easily implemented by the meterdata users. An additional benefit of having the applications residing onthe network rather than in the meter is that feature upgrades or meterupdates or maintenance occurs at the network level rather that in themeter at the customer's site. Thus, by decreasing the complexity of themeter, the probability for errors at the meter level is decreased,making maintenance and upgrades easier and more efficient.

Using the virtually unlimited processing power and capacity of anetwork, the capabilities of a meter also become virtually unlimited.When a meter requires an upgrade or patch, a Meter Service Providercould “push” the new code to all affected meters with a single commandinstead of physically removing each and every affected meter andtransporting them to the meter shop for firmware/software upgrades. Theupgrades would take effect immediately, making the new functionalityinstantaneously available to meter data users.

In addition to allowing meter data users to directly access and processmeter data, the system allows meter data users to provide certain enduser processes (e.g., service disconnect, on-site usage display, etc.),as shown in FIG. 9. End users (i.e., energy consumers) could lease orpurchase applications from a meter data user, which would enable on-sitecontrol and monitoring of energy consumption, usage, etc. Appliancesthat implement embedded network-enabling devices can be managed andmonitored by the meter data user and/or the end-user. An added featurefor the end-user is in the field of home or business automation forbuilding and energy management. Currently, end-user devices andapplications designed for home/business automation must implement one ofa variety of protocols (e.g., LonWorks, CEBus, X10, etc.). In thepresent system, a common communication protocol (TCP/IP) unifiesdevelopment of automation devices and applications. Such a system wouldenable end-user pre-payment, real-time and “energy exchanges” pricing,and even on-site payment via a card reader. Energy managementapplications (like demand management or load shedding) could be easilymonitored and configured by both the meter data user and the end-user.

CONCLUSION

With this invention, the meter data user, or MDU, that decides upon anexclusive ownership business model will be capable of assemblingservices provided by many suppliers to create the AMR System that bestsuits their business case. In addition, the MDU can elect to developcertain services to add value or lease to other MDUs. This increases aMDU's flexibility to generate revenue, reduces their dependence upon asole AMR System provider, and reduces their overall risk. This inventionalso strengthens the service bureau business model by allowing a servicebureau operator to assemble and/or develop different services fordifferent MDU subscribers. These MDU subscribers can in turn developvalue-added services of their own in order to gain competitiveadvantage. Finally, this invention helps the AMR Suppliers by creatingwell-defined services that makeup an AMR System. The AMR Suppliers candecide which services they can best develop to generate an ongoingrevenue stream, not a series of one time, customized AMR System sales.

In sum, the present invention provides a novel system based on anetwork-enabled, extensible meter. It is understood, however, that theinvention is susceptible to various modifications and alternativeconstructions. There is no intention to limit the invention to thespecific constructions described herein. E.g., the various techniquesdescribed herein may be implemented in a variety of hardware orsoftware, or a combination of both. Preferably, the techniques areimplemented in utility metering components having programmableprocessors, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or disk storage elements), andvarious application programs. Each program may be implemented inassembly or machine language. However, the programs can be implementedin a high level procedural or object oriented programming language tocommunicate with a computer system. In any case, the language may be acompiled or interpreted language. Each such computer program ispreferably stored on a storage medium or device (e.g., ROM or magneticdisk) that is readable by a general or special purpose programmablecomputer for configuring and operating the computer when the storagemedium or device is read by the computer to perform the proceduresdescribed above. The system may also be implemented as acomputer-readable storage medium, configured with a computer program,where the storage medium so configured causes a computer to operate in aspecific and predefined manner.

Although exemplary embodiments of the invention have been described indetail above, those skilled in the art will readily appreciate that manyadditional modifications are possible in the exemplary embodimentswithout materially departing from the novel teachings and advantages ofthe invention. Accordingly, these and all such modifications areintended to be included within the scope of this invention as defined inthe following claims.

1. A networked-based, extensible metering system, comprising: (a) a TCP/IP network; (b) a directory service coupled to the TCP/IP network; (c) a plurality of network-enabled meters coupled to the TCP/IP network, different ones of the network-enabled meters having different communications interface protocols by which they communicate over the TCP/IP network, each of the network-enabled meters uploading its location and its respective communications interface protocol to the directory service; and (d) one or more network servers that execute a plurality of different applications, each application processing data collected from one or more of the network-enabled meters to provide a respective metering service, the applications communicating with the network-enabled meters using their respective communications protocols obtained from the directory service, wherein the one or more network servers permit different meter data users to purchase or lease different combinations of the metering services provided by the applications executing thereon.
 2. A system as recited in claim 1, wherein each network-enabled meter includes a network communication device.
 3. A system as recited in claim 1, wherein the TCP/IP network comprises the Internet.
 4. A system as recited in claim 1, wherein the TCP/IP network comprises an intranet.
 5. A system as recited in claim 1, wherein the TCP/IP network comprises a wide area network.
 6. A system as recited in claim 1, wherein said applications are upgradeable on the network.
 7. A system as recited in claim 1, wherein other applications are downloaded to one or more of the network-enabled meters and are activated on each meter on a real-time basis.
 8. A system as recited in claim 1, wherein multiple meter data users can purchase or lease the same or different metering services for the same meter.
 9. A system as recited in claim 1, wherein the meter consists of a reduced set of internal hardware and firmware required for traditional metering devices.
 10. A system as recited in claim 1, further comprising network-enabling adaptors that allow legacy metering devices to interface with the TCP/IP network and to communicate with the one or more network servers.
 11. A system as recited in claim 1, further comprising communications adaptors to allow protocol-dependent communication between users and applications and the network-enabled meters. 